Skip to content

Conversation

@kostyniuk
Copy link

@kostyniuk kostyniuk commented Dec 20, 2025

🎯 Changes

Update Next.js middleware description to match the Next.js 16 syntax.

βœ… Checklist

πŸš€ Release Impact

  • This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

  • Documentation
    • Updated the React framework comparison guide to reflect Next.js middleware changes: the new single server-side proxy replaces the deprecated Edge-runtime middleware and runs on the Node.js/runtime, with full access to server-side resources (for example, databases).

✏️ Tip: You can customize this high-level summary in your review settings.

@github-actions github-actions bot added the documentation Everything documentation related label Dec 20, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 20, 2025

πŸ“ Walkthrough

Walkthrough

Updated the React framework comparison doc to state that Next.js now runs a single proxy.ts file on the Node.js runtime (replacing deprecated middleware.ts) and that proxy.ts has full access to server-side resources like databases.

Changes

Cohort / File(s) Summary
Documentation update
docs/start/framework/react/comparison.md
Revised Next.js description: replaced mention of middleware.ts (Edge Runtime) with proxy.ts running on the Node.js runtime and noted proxy.ts has full server-side resource access. No code or logic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

πŸ‡ I nibbled lines where phrases mix,
Swapped middleware for trusty proxy fix,
A small hop, a tiny tweak,
Now docs hum clear and sleek,
Carrot-cheers for edits quick! πŸ₯•

πŸš₯ Pre-merge checks | βœ… 3
βœ… Passed checks (3 passed)
Check name Status Explanation
Description Check βœ… Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check βœ… Passed The title accurately describes the main change: updating the Next.js middleware description to reflect the transition from middleware.ts to proxy.ts runtime details.
Docstring Coverage βœ… Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❀️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

πŸ“œ Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 27d1c5e and 4745e4c.

πŸ“’ Files selected for processing (1)
  • docs/start/framework/react/comparison.md (1 hunks)
🧰 Additional context used
πŸ““ Path-based instructions (1)
docs/**/*.{md,mdx}

πŸ“„ CodeRabbit inference engine (AGENTS.md)

Use relative links to docs/ folder format (e.g., ./guide/data-loading) for internal documentation references

Files:

  • docs/start/framework/react/comparison.md

@brenelz
Copy link
Contributor

brenelz commented Jan 4, 2026

Some conflicts

Correct grammatical error in comparison of Next.js limitations.
Updated Next.js proxy.ts description to reflect runtime changes.
@kostyniuk
Copy link
Author

revised the update @schiller-manuel , @brenelz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Everything documentation related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants